Important info:
delete a user means:
The user will notified using the notification framwork and an "urgent" notification, which should be delivered by email and can not be unsubscribed. The user will be marked as deleted in the database, all running jobs will be cancelled, all sessions will be terminated and login is blocked.
However it will NOT delete all their data, histories etc. on the spot.
This only happens when a user is purged

Delete user functionality works as follows:
The user can specify the flag --delete-user <MIN_SEVERITY> , where <MIN_SEVERITY> must be one of the defined VALID_SEVERITIES (low, medium and high), this is not case sensitive.

Everytime the script matches a file in a jwd to the malware database,
and if the severity level of that malware is EQUAL OR HIGHER than the specified <MIN_SEVERITY>, the Galaxy user ID is added to a set named delete_users.

Once the iteration over the running jobs found in the databse is done, the script iterates over the delete_users set, requests an encoded version of their user ID from Galaxy's API (GALAXY_BASE_URL and GALAXY_API_KEY must be set in the ~/.bashrc file of the user running WALL·E) and then creates a notification that will stay in the database for 6 months and sends a DELETE request to /api/users/<encoded_id>.

• Once there is a notification framework with a mandatory email channel, the script shall send a message to that user before the deletion happens. (see https://github.com/usegalaxy-eu/issues/issues/514#issuecomment-1959158284)

The second, more minor change in this PR is the amount of information that is logged in verbosity mode:

- TIMESTAMP GALAXY_USER JOB_ID MALWARE_CLASS MALWARE MALWARE_VERSION PATH
+ TIMESTAMP MALWARE_SEVERITY USER_ID USER_NAME USER_MAIL TOOL_ID GALAXY_JOB_ID RUNNER_JOB_ID RUNNER_NAME MALWARE_CLASS OBJECT_STORE_ID MALWARE_VERSION PATH